Linear ticket

https://linear.app/vapi/issue/PRISM-978/gitops-support-cross-org-resource-migration-with-uuid-reference

Value

Customers can now bootstrap each org's credential and phone-number bindings into its gitignored environment file. This lets the same logical configuration move between orgs without copying secrets or hard-coding another org's UUIDs.

This PR provides the binding-discovery foundation and a complete dummy dev → staging → production example. The promotion command remains a separate deliverable under PRISM-978.

Evidence of value

• Setup and pull refresh a clearly marked binding block while preserving customer-managed environment values.
• Existing aliases remain stable by resource ID; unnamed or ambiguous phone-number matches are warned and omitted.
• The example shows identical logical resources with different UUIDs in three dummy orgs.
• Seven focused binding tests pass, and the TypeScript build passes.

API Changes (including webhooks + events)

• Is this changing the public API?

  • Yes
  • No

• If yes, is it backward‐compatible?

  • Yes
  • No

Non backward-compatible changes might break customers' agents. Please proceed with care and notify the team.

Testing plan

• Run npm run build.
• Run node --import tsx --test tests/bindings.test.ts.
• Run npm test; the current repository baseline is 265 passing and 20 known hash-store/migration failures, with no new failures from this change.
• In disposable orgs, run setup or bootstrap pull and verify that credentials and named phone numbers populate the managed .env.<org> block without provisioning resources.